Summary

Equivalent Azure Repos remotes could compile to different integrity locks when the local origin used the legacy visualstudio.com/DefaultCollection shape. That left ado-aw-metadata / aw_info.json source identity empty locally but populated in Azure Pipelines, causing deterministic integrity checks to fail.

• Remote normalization

  • Accepts legacy collection-prefixed remotes:

    https://{org}.visualstudio.com/DefaultCollection/{project}/_git/{repo}
    

  • Canonicalizes them to the same context as:

    https://dev.azure.com/{org}/{project}/_git/{repo}
    

  • Covers both parse_ado_remote() and parse_git_remote().

• Integrity regression coverage

  • Compiles the same workflow from temp git repos using legacy and modern Azure Repos remotes.
  • Asserts complete lock output is byte-identical and source metadata is populated.

• Failure-signal cleanup

  • Preserves ADO’s implicit success gate on trigger-conditioned execution-context steps:

    condition: and(succeeded(), <trigger predicate>)

  • Applies to PR, PR checks, work item, schedule, CI push, pipeline, and manual context steps.

Test plan

• cargo build
• cargo test
• cargo clippy --all-targets --all-features